-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix fuzz CI failures #3521
Fix fuzz CI failures #3521
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3521 +/- ##
==========================================
+ Coverage 88.34% 89.02% +0.68%
==========================================
Files 149 149
Lines 112915 116871 +3956
Branches 112915 116871 +3956
==========================================
+ Hits 99753 104044 +4291
+ Misses 10685 10406 -279
+ Partials 2477 2421 -56 ☔ View full report in Codecov by Sentry. |
Let's just finally figure out a secondary MSRV target for |
Sure, we could do that too. We should get that fixed ASAP, though, because it'd be nice to have passing CI to release 0.1... |
Alright, now opened a respective/alternative PR here: #3528 If we move forward with that I'll also land lightningdevkit/ldk-node#429, and when recently talking to BDK, they seemed happy to more or less follow whatever MSRV bump we propose. Also see bitcoindevkit/bdk#1750. |
9bb6358
to
5a771c3
Compare
Okay, will only fix fuzz CI failures here, though I still want to do that. |
Backported in #3536. |
No description provided.